home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr18
/
ace151.zip
/
FREQ.DOC
< prev
next >
Wrap
Text File
|
1993-05-17
|
37KB
|
1,031 lines
AceComm & Utilities (Tm)
Version 1.51
"Leading Software Technology" for todays Hi-Speed Modem
Evaluation copy 05/17/93
File Requests
AceComm & Utilities
Version 1.51
Copyright (c) 1990 - 1993 all rights reserved
by
ACE Programming Services & Michael G Phelps
This manual by Nick Grenfell
AceComm Support Services (602) 846-4563 Telephone
Michael G Phelps (602) 846-2940 BBS
Phoenix, AZ CompuServe 75120,3306
CONTENTS
Chapter 1 FILE REQUESTS.......................................1
NODELIST or optional .NOD file (FBL.EXE output)..1
Making a File Request............................2
Using AceComm with the full blown raw NODELIST...3
Using AceComm with FBL'S .NOD file...............4
MAKING A FIDO STYLE EMSI FILE REQUEST............6
Selecting a ZONE:NET/NODE Address................8
NODE Display Menu................................9
Entering Filenames for Request..................10
Dialing the NODE................................11
EMSI Handshaking................................12
.REQ File.......................................13
Further Explanations............................15
Chapter 1 FILE REQUESTS
NODELIST or optional .NOD file (FBL.EXE output)
NODELIST is a specially formatted ascii file listing all BBS
NODES which are members of a NETWORK known as FODONET. The
NODELIST contains the each system's name, location, phone number,
modem capability, mail capability. The NODELIST serves as a
giant phone directory for all FIDONET BBS systems world wide. As
of the writing of this manual, February 18, 1993, the FidoNet
nodelist is approximately 1.7 megabytes. This may sound huge at
first, but carrying the entire nodelist all the time is optional.
.NOD file (FBL.EXE output)
FBL can extract a NET from the NODELIST. Sample .NOD files are
contained inside FON.ARJ (included in the AceComm package)
Generally a NET will cover an entire city, and you may be content
holding a .NOD file for your city's NET, rather than a full blown
copy of the NODELIST.
To obtain a .NOD file for your city, you will initially need a
NODELIST to use with FBL.EXE. Your local SysOp may, if asked,
keep a local current .BBS, and .NOD file for your NET available
for download. .BBS ? FBL produces two files. An ascii .BBS
file in BBS LIST format, and a .NOD file, raw NODELIST format.
AceComm can directly read the .NOD file for MAIL activities.
CBF.EXE (included in the AceComm package) is a utility that
converts FBL's .BBS file into an AceComm compatible .FON file.
In short, FBL.EXE can produce a local listing of all FIDONET BBS
systems for your city, for both a dialing directory, and mailer
directory.
Page 1 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
Making a File Request
Make sure that your NODELIST or .NOD file is in the directory
"NODELIST" specified within PRM-data AREA. You may have defined
this area on installation, and can check or edit it now from
within AceComm itself with the <PrmDataMenus_LUI> MACRO AREA.
AceComm comes with the ALT-P key configured to the
<PrmDataMenus_LUI> MACRO.
╔═════════ACE.PRM Data Edit-Menus═══════╗ To get here, load
║ General Controls ║ AceComm, then from
║ Serial Port Setup ║ the terminal screen
║ KeyBoard Text Macros ║ press ALT-P (in the
║>Directories in use ║ default configuration).
║ Executable Menu ║ Select the DIRECTORIES
║ AutoDnLd Trigger Sequences ║ IN USE selection by
║ Curtain color ║ using the arrow keys.
║ Mass BOX-MENU attributes ║
║ AutoSave is ON ║
╚═══ Select Help Color Quit ══════════╝
Press the [enter] key and a new screen pops in over it.
╔═════════ACE.PRM Data Edit-Menus═══════╗
║ General Controls ║
║ Serial Port Setup ║
║ KeyBoard Text Macros ║
║╔═ Directories in Use Menu ═════════════════════════════════
║║ .FON files: C:\ACE\FON
║║ .CAP files: C:\ACE\CAPTURE
║║ .SCR files: C:\ACE\SCRIPT
║║ .KTS files: C:\ACE\KEY
║║ Downloads: C:\ACE\FILES
╚║> Nodelist: C:\ACE\NODELIST
╚═══ Edit Help Color Quit ═══════════════════════════════
Be sure that your NODELIST or .NOD file resides within the
PRM-data NODELIST directory.
Page 2 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
Using AceComm with the full blown raw NODELIST
This sub chapter applies to those who wish to use the raw
NODELIST with AceComm. There is a handy utility provided with
AceComm named IDX.EXE. IDX will create a small index file so
AceComm can use the nodelist more efficiently. Otherwise the
NET/NODE search function would have to scan the entire nodelist
each time you wanted to make a file request. The index file
created, NLIST.IDX is about 5k in size. NLIST.IDX contains as
it's first data entry, the name of the NODELIST it has been
compiled for.
If your system maintains a NODELIST applying NODEDIFF files or is
changed by other means, IDX must be re run accordingly.
Run IDX.EXE to create this NLIST.IDX file. There is more
specific documentation on IDX named IDX.DOC, but the syntax to
run IDX is: (at the DOS prompt)
IDX nodelist.nnn
Where nnn is the day number of the FidoNet<tm> nodelist that you
currently have.
Copy NODELIST.NNN and NLIST.IDX into the PRM-data AREA
directory label NODELIST.
Page 3 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
Using AceComm with FBL'S .NOD file
OK, you're reading this section because you don't want to carry
a ~2~ megabyte nodelist on your drive all the time. For those
who run nodes, it's almost a necessity, but if you don't, there
are options for you. When making a File Request, AceComm looks
for a NODELIST.nnn file and a NLIST.IDX file. If AceComm cannot
find those, it next looks for a .NOD file. .NOD files are made
with an supplied utility called FBL.EXE. FBL will extract a
particular NET out of the entire nodelist. For NET 1:114
(Phoenix,AZ,USA), the 1_114.NOD file. You still require a
current nodelist, but at least you do not need to keep it, at the
ready for AceComm. What you will need to do is:
NOTE: You may find it handy to contact your favorite
FIDONET SysOp and ask him to carry FBL.EXE output
.NOD and .BBS files for you. He will get a weekly
current BBS list for all FIDO NODES for his NET, and
you can use the .NOD file with AceComm's mailer
functions, and run the .BBS file past CBF.EXE for a
current .FON file of FIDO BBS systems for your area.
Instructions for creating a .NOD file with FBL.EXE
1. Put the NODELIST and FBL together in the same
directory.
2. Decide on what NET it is that you want to File Request
from.
3. Run FBL with the following syntax:
FBL.EXE nodelist.nnn [ZONE:]NET [phone-filter]
where 'nodelist.nnn' is a standard nodelist file.
* 'ZONE' is optional (defaults to Zone,1)
* 'NET' is any Net that is defined in the
nodelist beginning as:
Host,NET. FBL defaults to using the first Zone
found.
* phone-filter' is an optional parameter. This
will tell FBL to filter phone numbers found,
creating a local BBS list.
Page 4 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
Using AceComm with FBL'S .NOD file (continued)
Example: FBL NODELIST.115 282
Result: Will generate listing for NET 282, leave phone numbers
intact with the 1-(area code) so they can be dialed as
long distance if you live outside of that net.
Example: FBL NODELIST.115 1:114 1-602-
Result: Will generate listing for NET 114, stripping off the LD
part of phone numbers (1-602) to make them local dialing
numbers
FBL creates 2 files: ZONE_NET.nod, and ZONE_NET.bbs
ZONE_NET.NOD - is a listing for NET in raw-nodelist format. This
file is what you are going to be needing for
AceComm to do a File Request.
ZONE_NET.BBS - is a listing for NET in BBS-List format. This one
is just to read, display or print.
FBL (with no arguments will display a help screen)
After you are done with FBL, make sure that the .NOD file you
created is residing in the PRM-data AREA directory for NODELIST.
╔═ Directories in Use Menu ═══════════╗
║ .FON files: C:\ACE\FON ║
║ .CAP files: C:\ACE\CAPTURE ║
║ .SCR files: C:\ACE\SCRIPT ║
Be sure the NOD ║ .KTS files: C:\ACE\KEY ║
file is in this ║ Downloads: C:\ACE\FILES ║
directory -----> ║> Nodelist: C:\ACE\NODELIST ║
╚═══ Edit Help Color Quit ═════════╝
Page 5 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
MAKING A FIDO STYLE EMSI FILE REQUEST
From the terminal screen:
call <RProtocols_LUI> macro
AceComm default setup "PgDn" key
Press the PgDn key (3 on the keypad). The INTERNAL RECEIVE
PROTOCOL menu pops up.
________________________________________________________________
A.C.E. Communications Software
Evaluation copy, Version (Test)
Initializing Modem
ATZ
OK ╓─ Internal Protocols (Recv) ──╖
ATEL1S7=40 ║─Batch Capable────────────────║
OK ║>Zmodem ║
║ Ymodem ║
║ Ymodem 1k/Y ║
║ YmodemG ║
║─Single File──────────────────║
║ Xmodem ║
║ Xmodem 1k ║
║─User Defined─────────────────║
║ Externals ║
║ AutoDnlds ║
║─FIDONET EMSI FReq.───────────║
║ FileRequest ║
╙─ Select Help Color Quit ──╜
AceComm ▒ 1,2400,8N1 ▒ Ansi ▒ 11:05:48pm ▒
Page 6 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
MAKING A FIDO STYLE EMSI FILE REQUEST (continued)
Again, with the arrow keys, move the selector down to FileRequest
and press the [enter] key.
╓─ Internal Protocols (Recv) ──╖
║─Batch Capable────────────────║
║ Zmodem ║
║ Ymodem ║
║ Ymodem 1k/Y ║
║ YmodemG ║
║─Single File──────────────────║
║ Xmodem ║
║ Xmodem 1k ║
║─User Defined─────────────────║
║ Externals ║
║ AutoDnlds ║
║─FIDONET EMSI FReq.───────────║
║>FileRequest ║<-EMSI File Request selection
╙─ Select Help Color Quit ──╜
When you press [enter] now, an INPUT WINDOW appears asking for
the Zone, Net and Node that you want to REQUEST the file from.
╓─Input Window─────────────────────────────────────────────────
║>
║ Format => ZONE:NET/NODE
╙──────────────────────────────────────────────────────────────
ATZ
OK
ATEL1S7=40
OK
...
AceComm ▒ 1,2400,8N1 ▒ Ansi ▒ 11:07:03pm ▒
Page 7 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
Selecting a ZONE:NET/NODE Address
╓─Input Window──────────────────
║> 1:114/35 <-- enter target address here
║ Format => ZONE:NET/NODE
╙───────────────────────────────
ATZ
OK
Enter the target systems address in the fashion, ZONE number
first (1-6, Zone 1 is North America), followed by a colon (:),
followed by the NET number (114 is for the Phoenix area), next is
a forward slash (/), then the target systems NODE number each
FidoNet<tm> node has it's own unique address). An incomplete
address will result in an error as will entering a nonexistent
address. AceComm must be able to find that address in the
nodelist or it will not continue.
╓─Input Window──────────────────
║> 1:114/35
║ Format => ZONE:NET/NODE
╙──╔═══ Message Alert ═════════════════════════════════════════
ATZ ║ Address not found
OK ║
ATEL╚═══ Press any key to continue══════════════════════════════
OK
The error above is what is displayed if AceComm has exhausted
it's resources in attempting to find a match to the inputted
target address.
Otherwise, the address box (below) appears when AceComm has found
a match to the inputted address.
Page 8 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
NODE Display Menu
╓─Input Window──────────────────────
║╓─1:114/35────────────────────────────────────────╖
║║ System Name A.C.E._Software_Support ║
╙║ City Phoenix_AZ ║
║ Operator Name Michael_Phelps ║
║ Phone Number 1-602-846-2940 ║
║ Baud Rate 9600 ║
║ Flags V32,CM,XA ║
╙─File_Request Human_call Poll_for_mail Quit───╜
This box appears so you, the user can be certain this is the
target system you desire to File Request from.
If this is the correct node you wish to FReq from, press the
enter] key and AceComm will then query you for a filename(s) to
Request from the target system.
If a mistake was made and/or this was not the node that you
wanted to File Request from, hit [ESC] and AceComm will bring you
out.
System Name and City are self explanatory, the name of the system
that you have addressed your File Request to.
Operator Name is the name of the Sysop of the node you have
addressed your File Request to.
Phone number, of course is the phone number of the addressee of
your File Request. Do not be alarmed if the system is local to
you and the phone number still contains 1-(area code). AceComm
will filter that out for local calls.
Some systems do not carry the CM flag. The CM flag stands for
Continuous Mail, which means the system is up 24 hours a day,
waiting to send or receive mail, or in this case, File Requests.
If this node were to not have this CM flag, you would not be able
to File Request from it because it is probably not up and waiting
24 hours a day. AceComm should give you a warning if you attempt
to File Request from a non-CM system.
Page 9 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
Entering Filenames for Request
╓─Input Window─────────────────────────────────────────────────
║>FileName:
║─Input Window<ENTER> alone when done──────────────────────────
╙──────────────────────────────────────────────────────────────
This window is used to input the names of the files that you are
going to be requesting from the target node.
╓─Input Window─────────────────────────────────────────────────
║>FileName: files
║─Input Window<ENTER> alone when done──────────────────────────
╙──────────────────────────────────────────────────────────────
Enter a filename that you desire to File Request and press the
enter] key. You may continue requesting more files just by
entering another name when the INPUT WINDOW reappears. When you
are done with the list of files you wish to request, just press
enter] when AceComm asks you for another filename.
Consider File Requesting the filename "FILES" first from a
system. Generally, systems have a master list of files that are
available on their system.
So, you would type (when the INPUT WINDOW appears) is: files
<cr> <cr>
Next will appear the dialing box. AceComm will now attempt to
connect with the system whose node number you gave.
Page 10 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
Dialing the NODE
╓──Record Number─────────────────────────────────────────
║> System Name A.C.E._Software_Support
║ Phone Number 1-602-846-2940
║ Line Control 19200,8N1
║ Terminal Emulation Ansi
║ Dialing Prefix
║ AutoLogOn Script
║ Capture File
║ Password
║─Call History───────────────────────────────────────────
║ Last Connect Time 17 Feb 01:05:56am
║ Past Connections 0
║─Dialing Status─────────────────────────────────────────
║ Dial String ATEQ0X4L1DT846-2940
║ Modem Response
║ ReDials 0
║ Elapsed 00:01 00:
║ Timeout 48
╙─ Quit <SpaceBar>-ReCycle ─────────────────────────────
After you get a connect with the target system, you will see
something similar to what is below. Different front-end-mailers
will look differently, however, the results will be the same.
Page 11 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
EMSI Handshaking
AceComm currently is limited to EMSI handshaking for it's mail
session activities. Almost all BBS systems using front end
mailers such as Binkley, FrontDoor, DBridge are EMSI capable.
EMSI handshaking is the means the two softwares use for
exchanging identification data. Your identification data is
contained inside the file ACE.CFG. You will have edited the file
previous to making a File Request. The following screen is the
result of a successful EMSI log on with a Binkley system.
CONNECT 9600
Address 1:114/35@fidonet.org Using BinkleyTerm Version 2.56
490I_REQA77E your Escape key to enter the BBS, or wait a few mom
A.C.E. Software Support
Michael Phelps, Phoenix,AZ1-602-846-2940
BinkleyTerm, 9600, CM,XA,V32,V42b
Outgoing 00720023.REQ
FileSize 9
0 9 0 CPS 00:00 ZGHDR
With successful EMSI log on, AceComm sends the .REQ file. The
REQ file contains a list of filenames for request.
Page 12 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
.REQ File
The line below gives the status on the transfer of the REQ file.
After the target system, 1:114/35 reads the REQ file,
BinkleyTerm responds by sending back the file requested.
CONNECT 9600
Address 1:114/35@fidonet.org Using BinkleyTerm Version 2.56
490I_REQA77E your Escape key to enter the BBS, or wait a few mom
A.C.E. Software Support
Michael Phelps, Phoenix,AZ1-602-846-2940
BinkleyTerm, 9600, CM,XA,V32,V42b
Outgoing 00720023.REQ
FileSize 9
0 9 0 CPS 00:00 ZGHDR
Incoming c:\ace\files\1_114-35.arj
FileSize 15211
6144 2048 236 CPS 00:26 ZDATA
After the OUTGOING is an INCOMING. To the right it says
c:\ace\files\1_114-35.arj. This is where the file you requested
is going to and the actual name of the file sent in response to
"FILES".
I know, I know, you requested FILES, but you're getting a file
named 1_114-35.arj. Strange eh? Well, some systems allow you to
request files by the use of what is called MAGIC names. I won't
go into detail on how that works, but suffice it to say that you
can define MAGIC names for whatever you want. An example of this
would be for the nodelist. Each nodelist is named differently,
but the Sysop can tell his front-end-mailer to send the
appropriate one just by you requesting the MAGIC name, NODELIST.
Or for a nodes master list of files. Just FILE REQUEST the name
FILES and you should receive that file. This can also be done
for other files as well. Say the most current version of the
compression utility ARJ. You might not know the version number,
but possibly, all you would need to do is FILE REQUEST the
filename ARJ and see if that does it.
Page 13 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
.REQ File (continued)
When the .REQ file is done being sent, it will be deleted. If
you find an .REQ file at some time in your AceComm directory, it
is probably the result of a file request that wasn't completed.
If you examine the .REQ file, you can tell what you requested and
where it was intended on going to. If you read what is inside
the REQ file, with LIST or even TYPE it out, it will tell you
what file(s) you were requesting. To find out where the system
was you had intended on requesting this from, look at the name of
the .REQ file. In this case, it was:
00720023.REQ
Take it apart this way..
0072 (hex) = 114 (decimal)
0023 (hex) = 35 (decimal)
So your request was targeted at 114/35 (Zone 1 assumed).
Page 14 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
Further Explanations
──────────── Terminal screen during File Request ───────────────
CONNECT 9600 ( Connect acknowledgement and baud )
Address 1:114/35@fidonet.org Using BinkleyTerm Version 2.56
(target FidoNet address and
front-end-mailer identification)
490I_REQA77E your Escape key to enter the BBS, or wait a few mom
(target mailer REQuesting an EMSI
packet, that line partially
overwritten by target mailer
attempting to verify if the current
connect is human or another mailer)
A.C.E. Software Support
(target system name)
Michael Phelps, Phoenix,AZ1-602-846-2940
(target system Sysop, location and
phone number)
BinkleyTerm,9600,CM,XA,V32,V42b
│ │ │ │ (mailer I.D., baud rate and flags)
│ │ │ │
│ │ │ └ modem is V.42bis capable
│ │ └──── modem is V.32 capable
│ └──────── mailer type I.D.
└─────────── system is of a Continuous Mail typ
Incoming c:\ace\files\1_114-35.arj
(pathname of the file or packet that
is being exchanged)
FileSize 15211 (total size of packet/file)
Page 15 AceComm & Utilities (Tm)
Chapter 1 FILE REQUESTS
Further Explanations (continued)
6144 2048 236 CPS 00:26 ZDATA
│ │ │ │ └─ information
│ │ │ │ about what
│ │ │ └─ amount ZModem is
│ │ │ of time currently
│ │ └─ Characters already doing.
│ │ Per spent
│ │ Second transferring
│ │ transfer this file
│ │ rate, higher
│ └─ size of the better
│ the current
│ packet being
│ transferred.
│ In this case,
│ the packet size
└─ number of is 2048 bytes (2k)
bytes that
have already
been transferred
